home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group96a.txt
/
000009_icon-group-sender _Mon Jan 8 12:09:50 1996.msg
< prev
next >
Wrap
Internet Message Format
|
1996-09-05
|
1KB
Received: by cheltenham.cs.arizona.edu; Mon, 8 Jan 1996 06:10:27 MST
Message-Id: <AA04038.9601081214.scorch@uk.ac.tees>
Sender: <H.Lawson@tees.ac.uk>
From: "Hamish Lawson" <H.Lawson@tees.ac.uk>
Organization: University of Teesside
To: icon-group@cs.arizona.edu
Date: Mon, 8 Jan 1996 12:09:50 +0
Subject: Re: How does Icon compare to Perl?
Priority: normal
X-Mailer: Pegasus Mail/Windows (v1.22)
Errors-To: icon-group-errors@cs.arizona.edu
Status: O
Chris D. Tenaglia wrote:
> Perl is interpreted like old BASIC is interpreted. Each line has
> to be freshly loaded and parsed during execution, whereas, even
> an "interpreted" Icon program uses a pre-digested icode.
Much as I prefer Icon over Perl, I wouldn't want its claim to
superiority based in part on false assertions about its rivals :-).
As I understand it, when Perl is invoked it compiles the given script
into memory before running it, rather than parsing each line as the
script is executed. This implicit compilation stage undergone every
time a Perl script is run may account for the reported longer
execution time of Perl scripts compared to equivalent precompiled
Icon scripts.
| Hamish Lawson, School of Computing and Mathematics,
| University of Teesside, Middlesbrough, Cleveland, UK, TS1 3BA
| Tel: +44 1642 218121 x3611 Fax: +44 1642 342604
| E-mail: H.Lawson@tees.ac.uk